baremetal list: add --details - #2886

Change the --provision-state choice "managable" to "manageable" in
osism baremetal list.

Ironic's provision state is spelled "manageable". The misspelled
choice was passed to Ironic as a filter that no node can match, so
"--provision-state managable" always listed nothing, while the correct
spelling was rejected by argparse. Listing the manageable nodes was
therefore impossible with this option.

Add a test that "manageable" is accepted and forwarded to the node
query.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Roger Luethi <luethi@osism.tech>

Add a --details option to osism baremetal list. It appends five
columns to the table; without it the output is unchanged:

- State Since (UTC): when the node entered its current provision
  state, from Ironic's provision_updated_at. After a series of
  redeploys it shows which nodes have been redeployed and which still
  run their old installation.
- Target State: target_provision_state, i.e. where a node in a
  transitional state such as "wait call-back" is heading.
- Automated Clean: the node's automated_clean. Ironic's null means
  the node follows the conductor's [conductor]automated_clean, so it
  is shown as "default" rather than as False.
- Maintenance Reason: maintenance_reason, or Ironic's fault (e.g.
  "power failure") when Ironic put the node into maintenance itself.
- Last Error: last_error on a single line, cut to 80 characters.

Maintenance Reason and Last Error are free text; last_error in
particular can carry messages that originate from a BMC or the deploy
agent. Control characters in them (C0 and C1, which include ESC, BEL
and CSI as well as line breaks) are replaced with spaces before
printing, so an escape sequence prints as plain text instead of
reaching the operator's terminal, and the table stays one line per
node.

The plain node list returns only a few fields, so --details lists
the nodes with details=True. openstacksdk's Node resource does not
map provision_updated_at: Ironic sends the field, but the SDK drops
it while parsing the response. The new osism.utils.ironic module
therefore lists through a Node subclass, DetailedNode, that declares
the field. It goes through Node.list, the public method behind
conn.baremetal.nodes(), which sends details=True to /nodes/detail, so
the request and microversion negotiation are the same as the SDK's
own. The subclass can be removed once openstacksdk maps the field.

The subclass also repeats Node's "uuid" alternate-id declaration:
openstacksdk looks the alternate id up only in the class's own
__dict__, so a Node subclass without it reports None as every node's
id.

The module is imported only when --details is given, keeping
openstacksdk out of the command module's import.

Tests cover the columns and their formatting, the exact 80-character
Last Error cell, the control-character handling, and, by running
openstacksdk's real list code against a mocked baremetal proxy, that
the request goes to /nodes/detail with the filter and the negotiated
microversion and that uuid and provision_updated_at survive parsing.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Roger Luethi <luethi@osism.tech>